@title{FEXPORT}{Export to Foreign File}
 Transfers all the requested image, and auxiliary information from a
 source file to an output file. Only some supported GDB formats may
 be exported to. 

 See Also: FIMPORT, GDB, LINK, VECWRIT

1	PARAMETERS
 FEXPORT is controlled by the following global parameters: 

 Name     Prompt                                  Count   Type

 FILI     Database Input File Name                1-64    Char
 FILO     Database Output File Name               1-64    Char
 DBIW     Database Input Window                   0-4     Int
 DBIC     Database Input Channel List             0-1024  Int
 DBIB     Database Input Bitmap                   0-1024  Int
 DBVS     Database Vector Segment                 0-1024  Int
 DBLUT    Database Lookup Table Segment           0-1024  Int
 DBPCT    Database Pseudocolour Segment           0-1024  Int
 FTYPE    Output File Type                        1-3     Char
 FOPTIONS Output File Options                     0-64    Char

2	FILI
 Specifies the name of the PCIDSK database containing the data to be
 exported. 

@verbatim
  EASI>FILI="file_spec"

@end
2	FILO
 Specifies the name of the output file to be created. This file must
 not exist before FEXPORT is run. 

@verbatim
  EASI>FILO="file_spec"

@end
2	DBIW
 Specifies the image window to be read from the input channels. 

@verbatim
  EASI>DBIW=Xoffset,Yoffset,Xsize,Ysize
  EASI>                          | defaults to entire image

@end
2	DBIC
 Specifies the list of input channels to be read from FILI. 

@verbatim
  EASI>DBIC = i,j,k, ...

@end
  - Up to 1024 channels can be handled 
  - Up to 16 integer values can be specified 
  - Ranges of channels can be specified by using negative values. For
    example, {1,-4,10} is internally expanded to {1,2,3,4,10} 

2	DBIB
 Specifies the database bitmap segments to be transferred. 

@verbatim
  EASI>DBVS=i,j,...,p

@end
  - Ranges of segments can be specified with negative values. For
    example, {1,-4,10} is internally expanded to {1,2,3,4,10}. 
  - Up to 1024 segments can be specified. 
  - Duplicate segments are NOT allowed. 

2	DBVS
 Specifies the database vector segments to be transferred. 

@verbatim
  EASI>DBVS=i,j,...,p

@end
  - Ranges of segments can be specified with negative values. For
    example, {1,-4,10} is internally expanded to {1,2,3,4,10}. 
  - Up to 1024 segments can be specified. 
  - Duplicate segments are NOT allowed. 

2	DBLUT
 Specifies database lookup table segments to be transferred. 

@verbatim
  EASI>DBLUT=i,...j,k

@end
  - Ranges of channels/segments can be specified with negative
    values. For example, {1,-4,10} is internally expanded to
    {1,2,3,4,10}. 
  - Up to 1024 segments can be specified. 
  - Duplicate segments are allowed. 

2	DBPCT
 Specifies database pseudocolour table segments to be transferred. 

@verbatim
  EASI>DBPCT=i,...j,k

@end
  - Ranges of channels/segments can be specified with negative
    values. For example, {1,-4,10} is internally expanded to
    {1,2,3,4,10}. 
  - Up to 1024 segments can be specified. 
  - Duplicate segments are allowed. 

2	FTYPE
 Specifies the file format type of the output file. This is the
 abbreviated code for the file format. Some supported file format
 codes are: 

@verbatim
  EASI>FTYPE="TIF"               | Tagged Image File Format
  EASI>FTYPE="XWD"               | X Window Dump

@end
 The FORMATS topic lists all the FTYPE values for the supported
 formats. 

 See Also: {fexport|FORMATS}FORMATS

2	FOPTIONS
 File creation options. These are specific to the file format, and in
 each case the default of no options is legal. The FOPTIONS may be
 used to specify the compression schemes, file format subtype or
 other information. 

@verbatim
  EASI>FTYPE="TIF"       | TIFF
  EASI>FOPTIONS="LZW"    | Lempel-Ziv Welch compression.

@end
 The FORMATS topic lists all the FOPTIONS values for the supported
 formats. 

 See Also: {fexport|FORMATS}FORMATS

1	DETAILS
 FEXPORT is used to export an window of selected data layers in a
 PCIDSK file to a foreign file format. Image channels, bitmaps,
 vectors, LUTs and PCTs may be exported, though most formats do not
 support all of these data types.

 The user must explicitly list the channels (DBIC), bitmaps (DBIB),
 vectors (DBVS), LUTs (DBLUT) and PCTs (DBPCT) to be exported. As
 well the user may optionally provide a subwindow (DBIW) on the
 source database to export.

 For formats that support it, georeferencing information will also be
 written to the output file. It will be computed based on the
 contents of the georeferencing if the input file, and the window
 requested in DBIW.

 The FTYPE parameter is used to control the type of the output
 database. The full list of support output database types are listed
 in the FORMATS topic. Some formats require additional information to
 control the nature of the created output file, and these are
 supplied in the FOPTIONS parameter.

 Note that most formats have limitations on the data types, and
 number of layers, that can be stored. The user is responsible for
 only providing legal data combinations in DBIC, DBIB, DBVS, DBLUT
 and DBPCT. Illegal combinations will cause FEXPORT to terminate, or
 the generation of improper output files. 

1	FORMATS
 The following is the list of the exportable formats supported (Note
 that in the "Export File" panel of the "Works" programs FOPTIONS
 refers to the Options textfield, and FTYPE the Type option menu.): 

2	AGE (Arc/Info Generate)
 Arc/Info Generate vector files may be generated with an FTYPE of
 "AGE". One, and only one vector segment may be exported, and it's
 georeferencing system will be lost.

 When exporting to Arc/Info Generate format the output file will
 contain either points or lines, but not both. If the segment being
 output contains both the output file will contain one or the other
 and the user will not receive a run time warning that some of the
 data is being dropped.

 The FOPTIONS parameter is unused. 

 See Also: {GDB|Sup|HDF}GDB

2	BMP (Windows BMP and OS/2 BMP)
 Windows and OS/2 BMP files are supported for reading. However, only
 Windows BMP files can be exported. The user may specify 1 or 3
 channels or 1 bitmap to be written to the BMP file. If one channel
 is selected, then a PCT may also be written. 

 See Also: {GDB|Sup|BMP}GDB

2	DBF (xBase .dbf)
 xBase table files can be generated by selecting an FTYPE of DBF.
 xBase files are written from a vector layer, but ignore any vertex,
 or georeferencing information, writing only the attribute
 information.

 All attribute types except CountedInt are supported for write in
 xBase files; however, all fields are assign a maximum width when
 written based on the field formatting information. This means there
 is an upper limit on the size of string that can be written to a
 .dbf file, though this limit is established according to the field
 format width in the source layer.

 Only one vector layer can be written to a .dbf file, and no other
 datatypes can be written.

 The FOPTIONS parameter is unused. 

 See Also: {GDB|Sup|xBase}GDB

2	DXF (AutoCAD DXF)
 AutoCAD Data Interchange Files (DXF) may be generated with an FTYPE
 of DXF. If more than one GDB Vector Layer is exported then they will
 be stored as separate DXF Layers.

 The FOPTIONS value can be used to select 2D vertices or 3D vertices.
 The default value if FOPTIONS is not specified is 3D vertices. 

@verbatim
  FOPTIONS="2D"   | Do not use Z coordonate
  FOPTIONS="3D"   | use Z coordonate

@end
 See Also: {GDB|Sup|AutoCAD DXF}GDB

2	ERD (Erdas)
 Erdas format image files may be exported to by selecting an FTYPE
 value of "ERD". The Erdas file may contain any number of image
 channels of either eight bit or sixteen bit unsigned data types.

 Georeferencing information will be written to the Erdas file if it
 is Long/Lat or UTM.

 The FOPTIONS parameter is unused. 

 See Also: {GDB|Sup|Erdas}GDB

2	GRD (Arc/Info ASCII Grid)
 Arc/Info ASCII Grid interchange files can be written with an FTYPE
 of GRD. All grid files are written out as a single 16 bit signed
 raster layer. Grid files should be read into Arc/Info with the
 ASCIIGRID command.

 No other data types can be exported to a grid file. Georeferencing
 coordinates are written to the file, but the georeferencing system
 is not. That is .prj files are not produced.

 The FOPTIONS parameter is unused. 

 See Also: {GDB|Sup|Arc/Info Grid}GDB

2	GRS (GRASS Raster/Vector)
 GRASS is a public domain raster/vector GIS produced by the U.S.
 government. It is possible to export GRASS raster layers by
 specifying an FTYPE of "GRS". Only uncompressed 8 bit, and 16 bit
 raster layers can be exported, and each raster layer may only
 contain one channel of imagery.

 GRASS files must be placed in the correct location within a GRASS
 directory tree. The path provided should be for a file in the
 "cell" or "cellhd" directory. If a .grassrc is present in the
 users home directory it should be possible to specify a layer name
 without a fully specified path.

 GRASS vector files may also be exported by specifying an FTYPE of
 "GRS". The path provided for the output file will determine the type
 of file that is written out. Paths which include a "dig" directory
 in the path will result in a binary file, and paths which include
 "dig_ascii" will produce an ASCII file. In both cases, the
 attribute file will be written to the "dig_att" directory.

 The FOPTIONS parameter is unused. 

 See Also: {GDB|Sup|Grass}GDB

2	GXF (Geosoft ASCII)
 GXF Version 2.00 image files can be generated. They can only hold
 one channel.

 The FOPTIONS parameter is unused. 

 See Also: {GDB|Sup|GXF}GDB

2	IFF (LaserScan's text IFF)
 LaserScan's text format Files (IFF) may be generated with an FTYPE
 of IFF. If more than one GDB Vector Layer is exported then they will
 be stored as separate IFF Layers.

 The folowing attributes, if they exist, will have a special
 function: 

  - REPCode: Feature Code 
  - GroupId: FSN (Feature Serial Number) 
  - Angle: RO (Orientation for texts and symbols) 
  - Height: AC 3 
  - TextString: TX for text features 
  - ChildList: Used to group features linked by invisible lines 

 The FOPTIONS parameter is unused. 

 See Also: {GDB|Sup|LaserScan IFF}GDB

2	JPG (Joint Photographic Experts Group JFIF format)
 JPEG JFIF format files may be generated with an FTYPE of "JPG". Only
 one (greyscale) and three (RGB colour) bands may be exported to a
 jpeg file. FOPTIONS, if given is the numerical percent 'quality' of
 the resulting JPEG file. The default quality is 75. More quality
 implies a bigger image. The useful range of this parameter is
 approximately 15-90. 

 See Also: {GDB|Sup|Joint}GDB

2	HDF (Hierarchical Data Format)
 HDF format files may be generated with an FTYPE of "HDF". All image
 data types may be exported to HDF files; however, no bitmaps, LUTs,
 PCTs, vectors or georeferencing may be exported.

 The FOPTIONS parameter is unused. 

 See Also: {GDB|Sup|HDF}GDB

2	LIP (Gould LIPS)
 LIPS imagefile format files may be created with an FTYPE of "LIP".
 Only one band (monochromatic) or three band (colour) eight band
 files can be created.

 No georeferencing, or other auxiliary data can be exported to LIPS
 format. The FOPTIONS parameter is ignored for LIPS files. 

 See Also: {GDB|Sup|LIPS}GDB

2	LSC (LaserScan)
 LaserScan image files may be generated with an FTYPE of "LSC". Only
 eight bit image channels, and bitmap images may be exported. The
 following configurations are supported: 

  - 2: Greyscale (uncompressed), 1 Channel 
  - 3: Pseudocoloured Image (compressed), 1 Channel + PCT 
  - 4: RGB (24 bit uncompressed), 3 Channels 
  - 5: Bitmap (uncompressed), 1 Bitmap 
  - 7: Pseudocoloured Image (uncompressed), 1 Channel + PCT 

 The FOPTIONS string may contain the keywords "COMP" for compressed
 output, and/or "PCT" to add a pseudo colour table. This is currently
 only needed to differentiate between type 2, type 3 and type 7
 files.

 Example: 

@verbatim
  EASI> FOPTIONS="COMP PCT"      | Type 3 file.
  EASI> FOPTIONS="PCT"           | Type 7 file.
  EASI> FOPTIONS=""              | Type 2 file (if one channel given)

@end
 Georeferencing, and channel descriptor information is written to an
 ".aux" file in the same directory as the laser-scan file. 

 See Also: {GDB|Sup|Laser}GDB

2	NIT (NITF 1.1)
 NITF 1.1 files may be generated using an FTYPE value of "NIT". Only
 one channel greyscale NITF 1.1 files may be generated.

 The FOPTIONS string should be set to "LON" if the generated file is
 to have a Long/Lat georeferencing; otherwise it should be blank. At
 this time UTM NITF files cannot be generated. 

 See Also: {GDB|Sup|NITF}GDB

2	PIX (PCIDSK)
 PCIDSK files may be generated by specifying an FTYPE of "PIX".

 The generated file will (as usual) have all images channels of the
 same type which will be the "largest" of the input image data
 types. As well, bitmap, vector, lut and pct segments will be created
 as required. Georeferencing is transferred.

 The FOPTIONS parameter may be used to specify the interleaving of
 the image channels. The default is "BAND" and the alternate possible
 values are "PIXEL" and "FILE". File interleaved PCIDSK files are
 equivalent to those produced by the CIM2 PACE program.

 PCIDSK support is primarily provided so that the user can
 conveniently subset existing PDIDSK files. 

 See Also: {GDB|Sup|PCIDSK}GDB, CIM, CIM2

2	PPM (PPM/PGM/PBM)
 Greyscale (PGM), RGB (PPM) and bitmap (PBM) files may be generated
 by specifying an FTYPE value of "PPM".

 The provided data must match one of these three configurations: 

  - 1 Channel: PGM Greyscale. 
  - 3 Channels: PPM RGB. 
  - 1 Bitmap: PBM Bitmap. 

 Georeferencing information will be placed in an ".aux" file in the
 same directory.

 The FOPTIONS parameter is unused. 

 See Also: {GDB|Sup|PPM}GDB

2	RAW (Raw Binary)
 Raw binary files can be generated by setting the FTYPE to "RAW". The
 generated files may contain any image data types, but may not
 contain LUTs, PCTs, vectors or bitmaps.

 Georeferencing, and file layout information will be written to an
 ".aux" file in the same directory as the raw image file.

 The default image interleaving is band sequential, but this be
 overridden with the following FOPTIONS values. 

  - "BAND": The default band sequential. 
  - "PIXEL": The image data is pixel interleaved. 
  - "LINE": The image data is line interleaved. 

 See Also: {GDB|Sup|Raw}GDB, IMAGEWR

2	RNH (SPANS Raster)
 SPANS Raster interchange format (.RNH/.RNL) format is supported for
 export by selecting an FTYPE of "RNH". One or more bands of eight
 bit, 16 bit signed or 16 bit unsigned data may be exported. SPANS
 Raster format is the interchange format for the Tydac SPANS GIS and
 SPANS MAP products.

 The filename provided must always have an extension of ".rnh". A
 file with the same basename as the header (.rnh) file will be
 created for each band exported. These files will be assigned the
 same basename as the .rnh file, and an extension indicating which
 band it contains.

 Most PCI projections can be exported to SPANS Raster file. No other
 auxiliary information is exportable. The FOPTIONS parameter should
 always be defaulted. 

 See Also: {GDB|Sup|SPANS}GDB

2	RST (Works ASCII RST)
 Representation Style Table ASCII Format Files (RST) may be generated
 with an FTYPE of RST if it's possible to get a representation table
 from the source Layers. The RST File can contain only one layer.

 The FOPTIONS parameter is unused. 

 See Also: {GDB|Sup|RST}GDB

2	SHP (Arc/Info Shapefile)
 Arc/Info Shapefiles (.shp/.shx/.dbf) can be created by selecting an
 FTYPE of "SHP". One, and only one, vector layer may be exported to a
 single shapefile.

 The output filename for the shapefile to be created should have an
 extension of .shp or .shx. When written three files are created,
 with the same basename, and the extensions .shp, .shx and .dbf.
 Together these make a dataset with attributes.

 Shapefiles don't have georeferencing, nor are any other datatypes
 other than vector layers supported.

 The FOPTIONS value can be used to select a layer type to assign to
 the created Shapefile. The default value if FOPTIONS is not
 specified is to make the layer of type MULTIPOINT. 

@verbatim
  FOPTIONS="POINT"               | each shape is a single point
  FOPTIONS="ARC"                 | each shape is set of connected points
  FOPTIONS="MULTIPOINT"          ! each shape is a set of arcs
  FOPTIONS="POLYGON"             ! each shape is a set of closed arcs

@end
 Note that the PCI Shapefile translator will always generate
 MULTIPOINT and POLYGON shapes with a single "part", that is a
 single arc, or polygon. POINT layers can only contain shapes with a
 single point. 

 See Also: {GDB|Sup|Arc/Info Shape}GDB, {fexport|FORMATS|DBF}.dbf
           limitations

2	SQD (Siemens SICAD)
 Siemens SICAD format files (.SQD) can be created by selecting an
 FTYPE of "SQD". One, and only one, vector layer may be exported to
 an SQD file. The georeferencing units will be placed in comments at
 the beginning of the SQD file, but will be ignored by SICAD.

 The FOPTIONS parameter is unused. 

 See Also: {GDB|Sup|Siemens SICAD}GDB

2	SUN (Sun Rasterfile)
 Sun Rasterfiles may be created by setting an FTYPE value of "SUN".
 Sun rasterfiles may have any of the following configurations: 

  - 1 Channel: Greyscale image. 
  - 1 Channel + PCT: Pseudocoloured image. 
  - 3 Channels + 0-3 LUTs: RGB Image with options LUTs. 

 No georeferencing information is exported with the Sun rasterfile.

 The FOPTIONS parameter is unused. 

 See Also: {GDB|Sup|Sun}GDB

2	TBA (SPANS Table File}
 Spans Table files may be exorted by selecting an FTYPE value of
 "TBA". Only one vector layer can be specified for export. A single
 TBA file will be created containing the attributes of the vector
 layer. All data types are supported except for integer lists. No
 vertex data is supported by this format. To export attribute and
 vector data use the VEC/VEH format. 

 See Also: {GDB|Sup|Spans Vector Archive}GDB,
           {fexport|FORMATS|VEH}Spans VEC/VEH

2	TGA (Targa Rasterfile)
 Targa raster files may be created by setting an FTYPE value of "TGA"
 The type of Targa file created is dependent on the number of
 channels specified int the DBIC parameter. 

  - 1 Channel: Greyscale image 
  - 3 Channels 24-bit uncompressed True-colour image 

 No georeferencing information is exported with the Targa rasterfile.

 The FOPTIONS parameter is unused. 

 See Also: {GDB|Sup|Tar}GDB

2	TIF (TIFF)
 TIFF format files may be exported to by selecting an FTYPE value of
 "TIF". The following are the valid configurations possible for TIFF.
 

  - 1 Channel: Results in a TIFF G or greyscale file. 
  - 1 Channel + PCT: Results in a TIFF P or Pseudocoloured file. 
  - 3 Channels: Results in a TIFF RGB file. 
  - 1 Bitmap: Results in a TIFF B or bitmap file. 

 TIFF files only support eight bit data at this time. Georeferencing
 information is exported in GeoTIFF format.

 The following values of FOPTIONS are possible to select different
 compression schemes: 

  - NONE: No compression, also selected if FOPTIONS is blank. 
  - LZW: Lempel-Ziv Welch. 
  - PACKBITS: Macintosh PackBits format. 
  - FAX3: CCITT Fax 3, only suitable for bitmaps. 
  - FAX4: CCITT Fax 4, only suitable for bitmaps. 

 As well it is possible append the attribute WORLD to the FOPTIONS
 value, separated from other text by a space, in order to request
 that an Arc/Info style TIFF World file be generated. 

@verbatim
  EASI> FOPTIONS = "LZW WORLD"

@end
 See Also: {GDB|Sup|TIFF}GDB

2	VEH (Spans Vector Archive VEC/VEH)       
 Spans Vector Archive Format files may be exported by selecting an
 FTYPE value of "VEH". Only one layer can be specified for export. A
 .VEC and .VEH file will be produced containg an ARC layer. Any
 attributes assocatied with the layer will be written out as a
 corresponding .TBA file. 

 See Also: {GDB|Sup|SPANS Vector Archive}GDB

2	XWD (X Window Dump)
 X Window Dump raster files can be generated using an FTYPE of "XWD".
 Currently only greyscale and 24 bit RGB X Window Dump files can be
 created, and no georeferencing or other auxiliary information is
 exported.

 The FOPTIONS parameter is unused. 

 See Also: {GDB|Sup|X Window Dump}GDB

1	EXAMPLE
 The user wishes to export bitmap segment 9 from irvine.pix to a
 CCITT Fax 3 compressed TIFF file. 

@verbatim
  EASI>FILI="/pci/demo/irvine.pix"
  EASI>FILO="lake.tif"
  EASI>DBIB=9
  EASI>FTYPE="TIF"
  EASI>FOPTIONS="FAX3"
  EASI>RUN FEXPORT

@end
